Repository navigation
Prepare native Server 3.14.0 - #1247
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <[email protected]>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Release preparation for native Server 3.14.0: the published Compose default moves to
durableworkflow/server:3.14.0, anddocs/releases/3.14.0.mdis added. Same shape as #1237, plus two one-line doc edits that change "native source, unreleased" to "native Server 3.14.0" for #1184.This release requires the
schema-upgradestep (#1246 addsdw_child_supervisions): SQLite 15→16, PostgreSQL 16→17, MariaDB 16→17, MySQL 17→18. After the step, going back to 3.13.x means restoring the backup. A 3.13.x binary refuses the upgraded database withnative_schema_newer_than_binary; it does not ignore the table (schema_upgrade::marker_refusal, 3.13.0 source).Ships since 3.13.0:
409 query_history_unavailablefor pruned or missing history.capabilities.worker_build_retirement).GET /metricsPrometheus scrape for autoscalers (capabilities.prometheus_text_metrics,DW_METRICS_TOKEN).duplicate_policy. A duplicate running id now returns a typed409 activity_already_startedinstead of 422.After merge: tag
3.14.0on the merge commit, then run native-release, image parity, published Compose, alias promotion, the GitHub Release and the Helm chart PR, as for 3.13.0. The chart takes a MAJOR bump (4.0.0) because of the schema step, as Chart 2.0.0 and 3.0.0 did.🤖 Generated with Claude Code